Overnight Research: Sub-Agent Architecture & Domain Overlap - 2026-03-01

1. Recommended Sub-Agent Architecture (Shared vs. Domain-Specific)

For the Ford Estate multi-agent system, a hybrid sub-agent architecture is recommended, combining the strengths of both shared service sub-agents and domain-specific parent agents.

Key Principles:

• Domain-Specific Parent Agents: Ada (coordination), K2 (tech), Cora (real estate), Winston (family), and Synergy (wife) will serve as the primary, persistent, domain-specific agents. They will manage high-level tasks within their respective areas.
• Shared Service Sub-Agents: For cross-cutting functionalities like document retrieval, deep research, and complex analysis or coding, dedicated "service-oriented" sub-agents should be implemented. These sub-agents can be invoked by any parent agent, reducing duplication of specialized capabilities.
  • Examples:
    • Deep Research Agent: A sub-agent dedicated to extensive web searches, synthesizing information, and generating reports.
    • Document Retrieval/RAG Agent: A sub-agent for querying knowledge bases, internal documents, or performing Retrieval-Augmented Generation (RAG).
    • Coding Agent: A sub-agent capable of handling coding tasks, potentially integrating with tools like Claude Code or reviewing PRs.
• Hybrid Approach for Context:
  • Parent agents will delegate tasks to shared service sub-agents, injecting domain-specific context as part of the prompt or task definition. This allows the general-purpose sub-agent to produce tailored results.
  • Initial context can be passed during sub-agent spawn (e.g., specific research question, relevant document IDs).
  • Dynamic context updates or clarifications can be sent via sessions_send during the sub-agent's execution.
• Tool Access Patterns:
  • Shared Service Sub-Agents: Should have read-only access to general information sources (web search, public APIs). They may have read-write access to shared knowledge bases or scratchpads for their specific task.
  • Domain-Specific Parent Agents: Will retain full read-write access to their domain's tools and data (e.g., K2 to homelab tools, Cora to real estate databases) and will decide when and what to delegate to shared sub-agents.
• Lifecycle:
  • Spawn-Task-Dispose: Most shared service sub-agents performing individual queries or analyses should follow a spawn-task-dispose lifecycle to ensure strong session isolation, resource efficiency, and prevent cross-session contamination (as seen in AWS Bedrock AgentCore).
  • Persistent Memory for Parent Agents: The main parent agents (Ada, K2, Cora, Winston) require a robust persistent memory mechanism (e.g., MEMORY.md in OpenClaw, or a dedicated vector database as indicated by starred repos like memsearch) to maintain their personas, long-term knowledge, and ongoing tasks across sessions. Per-agent memory isolation using agentId (as discussed in mem0 issues) is a good pattern for this.
• Result Aggregation: Ada, as the central coordinator, will be responsible for aggregating results from multiple sub-agents. This can involve LLM-based synthesis, comparing outputs, or even initiating a "debate" among agents for complex decisions, similar to hybrid patterns where a slower, deliberate agent aggregates faster specialists' outputs.

2. GitHub Starred Repos Analysis (Top 15 by Integration Value)

Sean's starred GitHub repositories reveal a strong interest in AI agents, local LLMs, self-hosting, and robust infrastructure for these systems. Here are the top 15 by integration value for Ford Estate:

1. BerriAI/litellm (AI/LLM Utilities, Infrastructure Tools) - HIGH: Crucial for LLM routing, cost management, and API integration across various models (OpenAI, Anthropic, etc.). Directly supports Sean's need for an OpenRouter replacement.
2. janhq/jan (AI/LLM Utilities, Infrastructure Tools) - HIGH: Offers an open-source, offline LLM chat UI. Excellent for privacy-conscious local LLM use, aligning with K2's domain.
3. HKUDS/nanobot (OpenClaw Related, Agent Frameworks) - HIGH: "Ultra-Lightweight OpenClaw" suggests interest in efficient, minimal agent deployments, valuable for resource-constrained environments or specific sub-agent roles.
4. zeroclaw-labs/zeroclaw (Agent Frameworks, OpenClaw Related, Infrastructure Tools) - HIGH: A fast, small, fully autonomous AI assistant framework that can be deployed anywhere. Highly relevant for scaling autonomous capabilities.
5. hesamsheikh/awesome-openclaw-usecases (OpenClaw Related, Agent Frameworks) - HIGH: Provides practical examples and inspiration for how OpenClaw can be applied across various domains, directly valuable for Ada's coordination and skill development.
6. accomplish-ai/accomplish (Agent Frameworks) - HIGH: An open-source AI coworker that lives on the desktop. This could inspire personal agent features for Winston or K2.
7. nearai/ironclaw (OpenClaw Related, Agent Frameworks, Infrastructure Tools) - HIGH: An OpenClaw-inspired Rust implementation focused on privacy and security. This is paramount for Ford Estate, especially for K2's oversight.
8. SamurAIGPT/awesome-openclaw (OpenClaw Related, Agent Frameworks) - HIGH: A comprehensive curated list of OpenClaw resources. An indispensable guide for navigating the OpenClaw ecosystem.
9. moltis-org/moltis (OpenClaw Related, Agent Frameworks, Infrastructure Tools) - HIGH: Rust-native, sandboxed, secure, and self-hosted "claw." Reinforces the importance of secure, auditable, self-hosted agent infrastructure.
10. jontsai/openclaw-command-center (OpenClaw Related, Infrastructure Tools, Agent Frameworks) - HIGH: An AI assistant command and control dashboard for OpenClaw agents. Essential for Ada (coordination) and K2 (tech) to monitor, control, and optimize agents.
11. HKUDS/ClawWork (OpenClaw Related, Agent Frameworks) - HIGH: "OpenClaw as Your AI Coworker" highlights practical, value-generating applications, informing how agents can contribute directly.
12. maxritter/pilot-shell (Agent Frameworks, AI/LLM Utilities) - HIGH: Professional development environment for Claude Code, focusing on reliable, production-grade code generation. Extremely valuable for K2's coding tasks.
13. HKUDS/FastCode (AI/LLM Utilities, Agent Frameworks) - HIGH: Aimed at accelerating code understanding. This can be a core capability for a coding sub-agent under K2.
14. zilliztech/memsearch (AI/LLM Utilities, Agent Frameworks, OpenClaw Related) - HIGH: A Markdown-first memory system for AI agents, inspired by OpenClaw. Crucial for implementing robust persistent memory and RAG capabilities across all agents.
15. heilcheng/awesome-agent-skills (Agent Frameworks, AI/LLM Utilities) - HIGH: A curated list of skills, tools, tutorials for AI coding agents. A resource for developing and expanding the skill sets of K2 and other sub-agents.

3. Reddit Communities for Daily Monitoring

These subreddits are highly relevant for continuous learning and community insights. A proposed monitoring schedule could involve daily checks for high-priority communities and weekly checks for medium priority.

• r/OpenClaw
  • Value: CRITICAL (TECH/ADA)
  • Key Topics: Platform updates, skills, use cases, security concerns.
  • Proposed Monitoring: Daily.
• r/MachineLearning
  • Value: HIGH (TECH/ADA)
  • Key Topics: General ML/AI breakthroughs, academic and technical discussions.
  • Proposed Monitoring: Daily/Bi-daily (for Ada to stay generally informed).
• r/LocalLLaMA
  • Value: HIGH (TECH/ADA)
  • Key Topics: Local LLMs, self-hosting, Llama models.
  • Proposed Monitoring: Daily (for K2, and Ada to monitor broader trends).
• r/ClaudeAI
  • Value: HIGH (TECH/ADA)
  • Key Topics: Anthropic models (Claude, Claude Code), user experiences, technical questions.
  • Proposed Monitoring: Daily (for K2 and Ada, given potential for Claude integration).
• r/CrewAI / r/CrewAIInc
  • Value: HIGH (TECH/ADA)
  • Key Topics: Multi-agent frameworks, orchestration, delegation patterns.
  • Proposed Monitoring: Daily (for Ada, to inform architectural decisions).
• r/homelab
  • Value: HIGH (TECH/K2)
  • Key Topics: Homelab setups, projects, sysadmin advice, hardware.
  • Proposed Monitoring: Daily/Bi-daily (for K2, for infrastructure management).
• r/selfhosted
  • Value: HIGH (TECH/K2)
  • Key Topics: Self-hosted software alternatives, general self-hosting practices.
  • Proposed Monitoring: Bi-daily (complementary to r/homelab).
• r/Proxmox
  • Value: HIGH (TECH/K2)
  • Key Topics: Proxmox hypervisor usage, virtualization.
  • Proposed Monitoring: Bi-daily (for K2, given Sean's Proxmox usage).
• r/realestate
  • Value: HIGH (CORA)
  • Key Topics: Real estate market trends, buying/selling, investment.
  • Proposed Monitoring: Daily (for Cora to stay informed on market dynamics).
• r/AutoGPT
  • Value: MEDIUM (TECH/ADA)
  • Key Topics: Autonomous agents, framework evolution, capabilities.
  • Proposed Monitoring: Weekly (for broader understanding of autonomous agent challenges and trends).

4. Specific Implementation Recommendations for Ford Estate

Based on the research, here are specific recommendations for the Ford Estate multi-agent system:

1. Establish Core Shared Services:
   • Immediately develop and deploy dedicated Deep Research and Document Retrieval/RAG sub-agents. These will be foundational capabilities for all parent agents.
   • These shared sub-agents should be designed to be stateless for individual queries, following the spawn-task-dispose model for efficiency and isolation.
2. Implement Robust Persistent Memory:
   • Prioritize integrating a persistent memory system, possibly inspired by zilliztech/memsearch, for all parent agents (Ada, K2, Cora, Winston). This will allow them to retain context and knowledge across sessions.
   • Ensure per-agent memory isolation is properly implemented to prevent cross-contamination.
3. Leverage LLM Routing & Gateway:
   • Investigate and potentially integrate BerriAI/litellm as a central LLM routing proxy. This will provide flexibility in model choice, enable cost tracking, and implement guardrails, aligning with Sean's existing interest in an OpenRouter replacement.
4. Embrace Local LLM Capabilities:
   • Explore janhq/jan for incorporating offline, local LLM capabilities, enhancing privacy and reducing reliance on external APIs where possible. This is a direct fit for K2's domain.
5. Utilize OpenClaw-Specific Tools & Resources:
   • Regularly consult SamurAIGPT/awesome-openclaw and hesamsheikh/awesome-openclaw-usecases to discover new skills, best practices, and use cases for OpenClaw.
   • Monitor HKUDS/nanobot and moltis-org/moltis for insights into lightweight, secure, and self-hosted OpenClaw implementations.
6. Develop a Command & Control Dashboard:
   • Consider implementing a dashboard similar to jontsai/openclaw-command-center for Ada and K2 to effectively monitor agent activity, manage tasks, and get an overview of the multi-agent system's health and performance.
7. Focus on Security and Reliability:
   • Given the findings on r/OpenClaw regarding malicious skills and nearai/ironclaw's focus on privacy and security, a strong emphasis must be placed on auditing skills, implementing robust sandboxing, and ensuring the overall security posture of the OpenClaw deployment.
8. Automate Reddit Monitoring:
   • Set up automated daily monitoring of the high-priority Reddit communities, with Ada synthesizing key takeaways and alerting relevant parent agents (K2 for tech, Cora for real estate) to critical discussions or trends. Weekly summaries for medium-priority communities.
9. Iterative Skill Development:
   • Use resources like heilcheng/awesome-agent-skills to continuously identify and develop new, specialized skills for various sub-agents as needed, enhancing the system's capabilities incrementally.
10. Refine Coding Agent Workflow:
    • For K2's coding tasks, consider integrating methodologies from maxritter/pilot-shell to improve reliability, ensure testing, and preserve context for production-grade code. Leveraging HKUDS/FastCode could enhance code understanding.